Vestibule structure for cooling redundancy in data center

ABSTRACT

A system includes multiple modular hot aisle cooling units (MHACUs) arranged in a series in a data hall, each MHACU configured to cool multiple servers in the data hall, the servers arranged in multiple containment modules within the data hall, each containment module comprising a hot aisle. The system also includes multiple vestibules, each connected to the hot aisles of at least two of the multiple containment modules and configured to allow heated air to flow between the hot aisles. The system also includes a pump package configured to provide cooling fluid to the multiple MHACUs. The system also includes at least one computing device configured to control at least one of air throughput, leaving air temperature, or leaving fluid temperature in each of the multiple MHACUs to customize cooling levels to different ones of the multiple containment modules.

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY CLAIM

This application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 63/303,465 filed on Jan. 26, 2022, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

Embodiments of the present disclosure relate to cooling systems and, in particular, to a vestibule structure for cooling redundancy in a data center.

BACKGROUND

Colocation data centers typically require flexibility in space utilization to accommodate diverse customer requirements. For example, some colocation data centers must be equipped to provide space for both ASHRAE (American Society of Heating, Refrigerating, and Air-Conditioning Engineers) allowable and ASHRAE recommended customers. Many data center providers prefer closed systems, in which no direct outside air or liquid is supplied to the data hall for cooling.

SUMMARY

This disclosure provides a vestibule structure for cooling redundancy in a data center.

In a first embodiment, a system includes multiple modular hot aisle cooling units (MHACUs) arranged in a series in a data hall, each MHACU configured to cool multiple servers in the data hall, the servers arranged in multiple containment modules within the data hall, each containment module comprising a hot aisle. The system also includes multiple vestibules, each connected to the hot aisles of at least two of the multiple containment modules and configured to allow heated air to flow between the hot aisles. The system also includes a pump package configured to provide cooling fluid to the multiple MHACUs. The system also includes at least one computing device configured to control at least one of air throughput, leaving air temperature, or leaving fluid temperature in each of the multiple MHACUs to customize cooling levels to different ones of the multiple containment modules.

In a second embodiment, a method includes providing, via a fluid supply line, cooling fluid from a pump package to a first MHACU among multiple MHACUs arranged in a series in a data hall, each MHACU configured to cool multiple servers in the data hall, the servers arranged in multiple containment modules within the data hall, each containment module comprising a hot aisle, wherein at least some of the hot aisles are connected via multiple vestibules that allow heated air to flow between the at least some hot aisles. The method also includes determining that a temperature of the cooling fluid in the first MHACU has risen to a first temperature that is less than a predetermined maximum temperature. The method also includes, in response to the determining that the temperature of the cooling fluid in the first MHACU has risen to the first temperature, providing at least some of the cooling fluid to a second MHACU among the multiple MHACUs. The method also includes determining that the temperature of the cooling fluid in the second MHACU has risen to a second temperature that is at least the predetermined maximum temperature. The method also includes, in response to the determining that the temperature of the cooling fluid in the second MHACU has risen to the second temperature, providing the cooling fluid to a fluid return line for return to the pump package.

Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example cooling system for cooling a data center according to this disclosure;

FIG. 2 illustrates further details of one example of a modular hot aisle cooling unit (MHACU) according to this disclosure;

FIG. 3A illustrates details for improving the efficiency of heat rejection through increased thermal content of fluid, according to this disclosure;

FIG. 3B illustrates a plan view of a data hall in which the efficiency improvement techniques of FIG. 3A are used, according to this disclosure;

FIGS. 4A through 4C illustrate example data halls with different levels of cooling density according to this disclosure;

FIGS. 5A through 5E illustrate example installations of cooling coils that can be used as one or more modular hot aisle cooling units (MHACUs) according to this disclosure;

FIG. 6 illustrates an example of a computing device for use in a cooling system according to this disclosure;

FIG. 7 is a flowchart illustrating an example of a cooling process using the cooling system of FIG. 1 according to this disclosure;

FIGS. 8A through 8C illustrate different views of an example data hall that includes one or more vestibules according to this disclosure;

FIGS. 9A through 9C illustrate different views of another example data hall that includes one or more vestibules in a different configuration according to this disclosure; and

FIG. 10 illustrates another example data hall that includes multiple vestibules in a grid configuration according to this disclosure.

DETAILED DESCRIPTION

FIGS. 1 through 10 , discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

For simplicity and clarity, some features and components are not explicitly shown in every figure, including those illustrated in connection with other figures. It will be understood that all features illustrated in the figures may be employed in any of the embodiments described. Omission of a feature or component from a particular figure is for purposes of simplicity and clarity and is not meant to imply that the feature or component cannot be employed in the embodiments described in connection with that figure. It will be understood that embodiments of this disclosure may include any one, more than one, or all of the features described here. Also, embodiments of this disclosure may additionally or alternatively include other features not listed here.

As discussed above, colocation data centers typically require flexibility in space utilization to accommodate diverse customer requirements. For example, some colocation data centers must be equipped to provide space for both ASHRAE allowable and ASHRAE recommended customers. Many data center providers prefer closed systems, in which no direct outside air or liquid is supplied to the data hall for cooling.

To address these and other issues, embodiments of the present disclosure provide indoor cooling systems for use with colocation data centers. The disclosed indoor cooling systems are designed to be operated at a wide range of fluid temperatures. The disclosed embodiments include cooling coils and immersion systems configured in different shapes and elevation to match the power and heat density of the prescribed supply air temperatures (SAT) for air cooling or entering fluid temperature (EFT) for liquid cooling, for computing device racks, computing device rows, computing device rooms, or computing device facility, in part or in whole. This system efficiency can be derived through the heat collection near the heat load, by removing the long air flow paths required in traditional colocation data center facilities from the compute device to the air handling equipment or the direct contact with a cooling fluid during immersion. The system efficiency can also be expressed in the amount of heat collected by way of the air to fluid transfer and/or fluid to fluid transfer through the custom configuration of cooling coils, location, sizes, shapes, and elevations. Additional efficiency can be found in the high Leaving Fluid Temperatures (LFTs) of the coils useable by fluid to fluid heat transfers performed within an immersion cooling system, and further efficiency through the higher quality heated fluid available to remote heat recover users or to remote heat rejection plant outside of the data hall.

FIG. 1 illustrates an example cooling system 100 for cooling a data center according to this disclosure. The embodiment of the cooling system 100 shown in FIG. 1 is for illustration only. Other embodiments of the cooling system 100 could be used without departing from the scope of this disclosure.

As shown in FIG. 1 , the cooling system 100 includes a data hall 110, a pump package 120, a fluid cooler 130, and a computing device 140.

The data hall 110 represents at least a portion of a colocation data center and is an enclosed space that houses a plurality of servers 112 that are arranged in server racks. As known in the art, the servers 112 generate substantial amounts of thermal energy that tend to heat the space inside the data hall 110, thereby requiring cooling to maintain the temperature of the data hall 110 at a suitable level for proper operation of the servers 112 and for comfort of any personnel inside the data hall 110.

The data hall 110 includes an indoor cooling system comprising one or more modular hot aisle cooling units (MHACUs) 114. The MHACUs 114 are disposed above, behind, and/or in front of the servers 112 and are operable to cool the servers 112. In particular, each MHACU 114 can be mounted above, behind, and/or in front of the server racks in the data hall 110. The MHACUs 114 can be configured in different shapes and sizes and installed at different elevations and in different arrangements and combinations, to match the power and heat density of the prescribed supply air temperatures for computing device racks, computing device rows, computing device rooms, or computing device facility, in part or in whole.

The MHACUs 114 cool the servers 112 by receiving heated air (e.g., approximately 130° F.-140° F. for ASHRAE allowable or approximately 100° F. for ASHRAE recommended) rising from the servers 112, cooling the heated air into cooled air (e.g., approximately 95° F. for ASHRAE allowable or approximately 80° F. for ASHRAE recommended), and outputting the cooled air to cool the servers 112. In some embodiments, the amount of air volume delivered by the MHACUs 114 to the data hall 110 is dependent on the amount of power delivered to the data hall 110. For example, the MHACUs 114 may deliver at least 80 cubic feet/minute (CFM) of air at a temperature of 80° F. (or at least 108 CFM of air at a temperature of 95° F.) for each one kilowatt (1 kW) of power delivered to the data hall 110.

Each MHACU 114 is modular, and sits above, behind, and/or in front of one or more of the racks of servers 112. FIG. 1 shows three MHACUs 114, but there may be more or fewer depending on the embodiment. The number of MHACUs 114 is easily scaled for the application and depends on the load density of the servers 112, the cooling capacity of each MHACU 114, and the like. In some embodiments, each MHACU 114 is capable of providing approximately 150 kW-700 kW of cooling capacity, although other embodiments can provide other cooling capacities.

The MHACUs 114 improve system efficiency over traditional techniques by handling heat collection near the heat load. That is, the MHACUs 114 remove the long air flow paths required in traditional colocation data center facilities from the computing device to the air handling equipment. Overall system efficiency can also be addressed in the amount of heat collected by way of the air-to-fluid transfer through the custom configuration of cooling coils, location, sizes, shapes, and elevations. Additional efficiency can be found in the high Leaving Fluid Temperatures (LFTs) of the coils to a remote heat rejection plant outside of the data hall 110.

The MHACUs 114 are designed to be operated at a wide range of fluid temperatures. Each MHACU 114 can be individually controlled (including air throughput, leaving air temperature, leaving fluid temperature, and the like) in order to customize cooling levels in real time in different parts of the data hall 110. For example, if some of the servers 112 generate a greater load and require additional cooling, then one or more MHACUs 114 in the vicinity of those servers 112 can be controlled to increase cooling capacity.

In some embodiments, the MHACUs 114 are connected in series and are fluidly coupled to the pump package 120. This can be referred to as a “serial topology.” In other embodiments, the MHACUs 114 can be connected in parallel. The connections to the MHACUs 114 can be formed individually, or in parallel or in series in any combination with each other or as a specific group, to produce the intended outcome, e.g., to collect the maximum amount of heat through an air-to-fluid transfer. Cooled fluid (e.g., approximately 90° F. for ASHRAE allowable or approximately 75° F. for ASHRAE recommended) received from the pump package 120 flows into each MHACU 114 and is used to cool the heated air from the servers 112. Once the fluid cools the heat air within the data hall 110, the heated fluid then returns to the pump package 120. In some embodiments, at least a portion of the heated fluid can be routed to one or more immersion tanks 145, as described in greater detail below. In some embodiments, the fluid is water, although other suitable fluids may be used and are within the scope of this disclosure.

In some embodiments, the system 100 also includes a heat recovery heat exchanger 150 for use in downstream heat recovery to support the needs of one or more heat recovery users. In some embodiments, the immersion tanks 145 can also generate higher quality heat suitable for downstream heat recovery. This high quality heat is available to the heat recovery heat exchanger 150 to support the needs of a heat recovery user.

FIG. 2 illustrates further details of one example of the MHACU 114 according to this disclosure. As shown in FIG. 2 , the MHACU 114 includes one or more variable speed fans 202, one or more fluid valves 204, and at least one coil 206 for transferring thermal energy from the heated air to the cooled fluid. The MHACU 114 also includes at least one control system 208 for controlling operation and speed of the fan(s) 202 and the position of the valve(s) 204. The at least one control system 208 is communicatively coupled to one or more sensors, including one or more pressure sensors 210, thermometers or other temperature sensors 212, equipment sensors 214, fluid flow sensors (not shown), and the like. In some embodiments, the temperature sensors 212 can measure, e.g., air temperature in the supply and return aisle, air temperature in the entering and returning air stream, fluid temperature in the supply and return lines, fluid temperature into and out of the coil 206, and the like. Fluid flow sensors can include direct fluid contact sensors, pipe surface contact sensors, infrared sensors, and the like. The type and number of sensors can be customized to direct specific fluid flow, air flow, fluid pressure, air pressure, thermal content of a prescribed fluid, thermal content of a prescribed air volume, relative humidity, and the like. The pressure sensors 210 can measure pressure differential between the supply air and return air aisle, fluid pressure at the input and output to the coil 206, and the like. Other sensors can include one or more anemometers to measure air velocity within the air flow stream, or one or more ultrasonic fluid flow sensors.

The valve(s) 204 can include any suitable valve(s) in any suitable combination for controlling fluid flow in and around the MHACU 114. Examples of the valve(s) 204 can include (but are not limited to) two-way control valves, three-way control valves, four-way control valves, six-way control valves, balancing valves, actuator controlled valves, thermal controlled valves, flow controlled valves, pressure controlled valves, and compensating valves.

In some embodiments, each fan 202 can be dynamically controlled or set to a specific fixed value to maintain the proper air supply volume, air temperature, or static pressure differential between the hot return air aisle and the cold supply air aisle, either individually or in combination with one or more attributes supporting the computing devices. In general, data sent from the sensors to the control system 208 can be used, individually or in any combination, to improve data center power efficiency, cooling efficiency, or to reduce total water consumption through the real time response to individual rack, row, room, or site cooling load demand. For example, the computing device power can be matched with the cooling supply provided based on the actual heat load calculated from the power demand of the computing device(s). Cooling efficiency can be improved by cooling only the amount of heat generated by the computing devices. Total water consumption can be reduced by not over-pumping through the cooling towers or adiabatic cooling spray cooling solutions and sustaining water losses from drift and surface evaporation. The effective control of computing device entering air temperature (EAT) and the control of the coil leaving fluid temperature (LFT) is configured through sensor input and programmed calculations to match the precise cooling demand requirements of the immediate rack, row, room, or site.

In some embodiments, the equipment sensors 214 are remote sensors employed at or around computing equipment (e.g., the servers 112) in the data hall 110 to detect or measure properties or parameters of the computing equipment. For example, the equipment sensors 214 can include onboard power sensors embedded in computing devices, servers, or network equipment to measure power used by the computing equipment. As another example, the equipment sensors 214 can include onboard thermal sensors or fan speed sensors embedded in computing devices, servers, or network equipment to measure heat generated by the computing equipment or a current fan speed of the equipment. As yet another example, the equipment sensors 214 can include onboard sensors for measuring CPU or hash rate utilization of the servers 112. These measurements can be provided to the control system 208 to control cooling. In some embodiments, room level thermal sensors can be used to override the local coil controls to meet a global (overall data center space) thermal requirement. In some embodiments, room level static pressure sensors can be used to override the local coil controls to meet a global positive pressure requirement for the supply air aisles.

In some embodiments, measurements collected by the equipment sensors 214 can be used as thermal heat load proxies. Through the real time monitoring and collection of the power outputs and known locations as described below, thermal heat load values can be calculated for a discrete area such as a device, a rack, a row, a room, a building, or a site.

The following are examples of electrical power measurement that can be used as a proxy for thermal heat load:

-   -   Device level: Power strip with individual point of connection         (POC) sensing output.     -   Rack level: Power sensors on local power strip(s) supporting the         devices inside a single rack.     -   Rack level: Individual power metered or monitored busway         electrical taps or circuit breakers directly supporting the         specific rack.     -   Row level: Busway input power sensing meter or individual         metering of electrical branch circuits supporting the row level         power distribution.     -   Room level: Power sensor input from data center distribution         panel(s), circuit breakers, metering sensors, or panel circuit         board metering.     -   Building level: Power sensor input from data center electrical         distribution boards and/or distribution circuit breakers         supporting the data center device critical load.     -   Site level: Power sensor monitoring of the site level electrical         sub-station output breakers to individual buildings where         computing devices are supported.

In some embodiments, control can be facilitated using Data Center Infrastructure Management (DCIM) techniques. As known in the art, DCIM can be used to describe processes, procedures, control inputs, and control outputs for micro and macro management of computing devices or data center infrastructure power and cooling. DCIM techniques can take into account individual or collective inputs from computing devices, computing equipment rack level aggregation of power and or cooling demand, computing device power or cooling demand aggregated at the row level, device power or cooling demand aggregation at the room level, building level aggregation of device power or cooling demand, site level demand of device power and cooling, and the like.

Once the thermal energy is transferred from the air to the cooled fluid, thereby heating the fluid, the heated fluid (e.g., approximately 120° F. for ASHRAE allowable or approximately 90.3° F. for ASHRAE recommended) is output from each MHACU 114 back to the pump package 120 and delivered to the fluid cooler 130 to reject the heat stored in the fluid. The leaving fluid temperature (LFT) from the coil 206 can be controlled through the position of the valve 204 and/or the air volume developed by the speed of the fan 202 and the leaving air temperature from the coil 206. In some embodiments, the control system 208 (which can be part of or include the computing device 140) simultaneously controls the temperature of the cooled air (leaving the MHACU 114 and entering the cold aisle) and the temperature of the heated fluid (leaving the MHACU 114) by varying both fan air volume and cooling fluid flow rate.

FIG. 3A illustrates details for improving the efficiency of heat rejection through increased thermal content of fluid, according to this disclosure. Conventional industry practices are inefficient at increasing and/or returning relatively high fluid temperatures to heat rejecting systems, due to inconsistent heat rejecting compute workloads within the data center, thermal dilution of the thermal content of the cooled supply fluid (e.g., from the combining of different temperature fluid flows) to the heat rejection system, and/or low supply fluid temperatures due to mixed supply air temperatures prescribed by the end user or computing equipment manufacturers. In general, low supply fluid starting temperatures result in relatively low return fluid temperatures. For example, some conventional systems exhibit heated returned fluid at a temperature of approximately 60° F.-75° F. Significant heat transfer and power efficiencies gains can be realized when the heated fluid leaving a heat rejection system can be returned at the highest fluid temperature the system design can accept (e.g., approximately 120° F. in some air cooled systems). That is, the greater the difference in temperature (Delta T) between the cooled supply fluid and the heated return fluid, the more efficiency is gained for the heat rejection plant and equipment. The details shown in FIG. 3A provide at least one solution to these issues.

As shown in FIG. 3A, multiple MHACUs 114 (identified here at 114 a-114 c) are fluidly coupled together in the data hall 110. While FIG. 3A shows three MHACUs 114 a-114 c, there may be more or fewer depending on the embodiment. Fluid supplied to the MHACUs 114 a-114 c is received from the pump package 120 via a fluid supply line 302. Heated fluid to be returned to the pump package 120 is carried via a fluid return line 304. Each MHACU 114 a-114 c is associated with a temperature sensor 311 a-311 c and a fluid control valve 321 a-321 c.

Initially, some or all of the cooled supply fluid from the pump package 120 is input into the first MHACU 114 a. The fluid moves through one or more coils 206 in the MHACU 114 a, absorbing thermal energy from the air of the data hall 110. This causes a rise in temperature of the fluid (as measured by the temperature sensor 311 a). If there is so much thermal energy absorbed by the MHACU 114 a that the fluid temperature rises to a predetermined maximum (e.g., 120° F.), then the control valve 321 a is controlled to return all the fluid to the fluid return line 304. Alternatively, if there is less thermal energy transfer, and the fluid temperature rises to a temperature (e.g., 75° F.) that is lower than the maximum, then the control valve 321 a is controlled to provide at least some of the fluid to the second MHACU 114 b.

In the second MHACU 114 b, fluid moves through one or more coils 206, absorbing thermal energy from the air of the data hall 110. This causes a rise in temperature of the fluid (as measured by the temperature sensor 311 b). If the MHACU 114 b absorbs enough thermal energy to raise the fluid temperature to the maximum, then the control valve 321 b is controlled to return all the fluid to the fluid return line 304. Alternatively, if there is less thermal energy transfer, and the fluid temperature rises to a lower temperature (e.g., 90° F.), then the control valve 321 b is controlled to provide at least some of the fluid to the third MHACU 114 c. This serial flow process continues until the maximum fluid temperature is reached or there are no more MHACUs in the series. In some embodiments, the fluid will return through the fluid return line 304 and enter or bypass one or more immersion tanks 352 according to the position of a control valve 321 d, which can route some or all of the fluid through the immersion tank(s) 352 or bypass the immersion tank(s) 352 on the way to the pump package 120. The immersion tank(s) 352 can represent (or be represented by) the immersion tank 145 of FIG. 1 .

The serial heating of the cooling fluid as shown in FIG. 3A can be enabled using input measurements of any or all sensors described above. The sensor inputs can be used with prescribed calculations, algorithms, and design protocols to control various components including the following:

-   -   Fluid flow rates at the individual coil, row, room, and/or site.     -   Fluid thermal release control point rates at the individual         coil, row, room, and/or site.     -   Fan speeds at the individual coil, row, and/or room.     -   System or individual fluid pressure for the individual coil,         row, and/or room.     -   System or individual air pressure settings at the row and/or         room level.     -   Pump speed at the row, room, and/or site level.     -   Fluid mixing ratios at the coil, row, and/or room level.

In some embodiments, the serial heating of the cooling fluid as shown in FIG. 3A can directly support the entering fluid temperature (EFT) for, e.g., data center immersion cooling using the immersion tank(s) 352, data center direct rack liquid cooling, district heating, heat recovery to one or more heat recovery users using a heat recovery heat exchanger 150, and the like.

FIG. 3B illustrates a plan view of a data hall 350 in which the efficiency improvement techniques of FIG. 3A are used, according to this disclosure. The data hall 350 can represent the data hall 110 of FIG. 1 . As shown in FIG. 3B, there is a serial thermal gain in the fluid (i.e., the temperature of the fluid increases from colder to hotter) across the data hall 350. This corresponds to possible zones in the data hall 350 that may have different cooling requirements. In some embodiments, the data hall 350 includes one or more of the immersion tanks 352. The immersion tanks 352 can accept high entering fluid temperatures (EFT) greater than 120° F., generate leaving fluid temperatures (LFT) greater than 150° F., and may be, in whole or in part, a component of the fluid return line 304.

In some embodiments, one or more of the MHACUs 114 does not include any air filters. Instead, the MHACUs 114 can rely on a dedicated outdoor air system (DOAS) pressurization unit to clean the air.

Use of the MHACUs 114 in the data hall 110 provides a number of advantageous benefits over existing solutions. Because the MHACUs are mounted above and/or behind or in front of the server racks, little or no floor space is required. Also, no duct work is required in the floor, which alleviates the need for a raised floor. This reduces infrastructures costs. The MHACUs 114 use less energy than existing solutions, due to no duct work losses, no under-floor distribution losses, and no filter pressure losses. The MHACUs 114 provide a modular design that offers flexibility in rack and load density. Local control of each MHACU 114 helps to ensure cooled air at a uniform temperature to the server rack air inlets.

The fluid cooler 130 receives heated fluid from the MHACUs 114 in the data hall 110 via the pump package 120. The fluid cooler 130 cools the heated fluid using a multi-coil heat exchanger system, and outputs the cooled fluid to the pump package 120 for delivery to the MHACUs 114 in the data hall 110. The fluid cooler 130 can include, but is not limited to, any suitable heat rejection equipment or feature, such as an open loop evaporative cooling tower or surface water routed through a heat exchanger, to isolate data hall cooling systems from external contaminants, closed circuit cooling tower, closed loop adiabatic cooling, air cooled chillers, conventional chiller systems, and the like. While FIG. 1 shows the cooling system 100 with one fluid cooler 130, this is merely one example. In other embodiments, the cooling system 100 could include multiple fluid coolers 130, each with isolated flow. In further embodiments, the cooling system 100 could include multiple fluid coolers 130 with combined flow for redundancy. In still other embodiments, the cooling system 100 could include multiple fluid coolers 130 with combined flow for cooling multiple data halls 110, thus providing increased redundancy at a lower cost.

As discussed above, the cooling system 100 includes one or more computing devices 140 to control the operations of the cooling system 100. In some embodiments, each computing device 140 may be a service operated by a third party such as a person or a company. Each computing device 140 may be housed and operated at a location different than the location at which the rest of the cooling system 100 is located. That is to say, each computing device 140 is not bound to a specific location.

FIGS. 4A through 4C illustrate example data halls 110 with different levels of cooling density according to this disclosure. In particular, FIG. 4A illustrates a data hall 110 with low density cooling (e.g., approximately 3 kW-9 kW per rack), FIG. 4B illustrates a data hall 110 with medium density cooling (e.g., approximately 15 kW-20 kW per rack), and FIG. 4C illustrates a data hall 110 with high density cooling (e.g., approximately 30 kW-50 kW per rack). As shown in FIGS. 4A through 4C, the number of MHACUs 114 disposed above each data hall can be increased to provide greater cooling density. In FIGS. 4A through 4C, the MHACUs 114 are shown as having a shape similar to an upside-down ‘V’. However, this is merely one example; in other embodiments, the MHACUs 114 could have any other suitable shape. For example, one or more of the MHACUs 114 could have a right-side-up ‘V’ shape, a TT′ or ‘W’ shape (either right-side-up or upside-down), a cone shape (either concave or convex to grade), or a flat coil face that is parallel to grade, or a flat coil perpendicular to grade. An embodiment with a flat coil shape, where the coil is in a position perpendicular to grade and directly behind or in front of the data center equipment racks, is an efficient and effective way to collect significant heat through air to fluid transfer. Such a coil can be used independently or in combination with overhead coils.

As discussed above, the MHACUs 114 can be configured in different shapes and sizes and installed at different elevations and in different arrangements and combinations, to match the power and heat density of the prescribed supply air temperatures for computing device racks, computing device rows, computing device rooms, or computing device facility, in part or in whole. For example, the MHACUs 114 can be installed overhead parallel to the back of the rack in a single file arrangement down the center of hot aisle, in a dual path parallel to the back of the rack, perpendicular to the back of the rack and encroaching over the tops of the rack's footprint on each side of the aisle, or in any combination of these. In some embodiments, the MHACUs 114 may be mounted with a surface adjacent to the backs of the racks as a rolling or moveable panel configuration. In addition, the mounting frame(s) for mounting the MHACUs 114 can include any one or more of the following features: adjustable frame height, support frame supported by floor, support frame hinges, support frame rollers, support frame suspended from above to any suitable structure, frame with mounting tool bars, frame with plug-and-play lighting, frame with plug-and-play controls and sensors, coolant and power distribution frame mounts, coolant and power distribution plug-and-play connections, and frame and enclosure sealed at, for example, 2% or less air bypass at 0.33 inches of water column (wc).

FIGS. 5A through 5E illustrate example installations of cooling coils 500 that can be used as the MHACUs 114 according to this disclosure. In particular, in the embodiments shown in FIGS. 5A through 5E, the coils 500 are disposed behind or in front of the equipment racks, instead of overhead. As shown in FIG. 5D, when the coils 500 are behind the equipment racks, the entering air is coming directly from the equipment being cooled. When the coils 500 are in front of the equipment racks, the entering air can be unconditioned and come from anywhere inside the room or space or from ambient air outside the room or building. The coils 500 can slide in a bypass arrangement (see, e.g., FIG. 5C), hinge or swing outward (see, e.g., FIG. 5A), or fold (e.g., bifold or accordion style) (see, e.g., FIG. 5B) behind the equipment racks. In some embodiments, the coils 500 can use the same supply fluid controls and return fluid features as the MHACUs 114.

In some embodiments, a coil 500 is greater than one data center equipment rack in width. In some embodiments, a coil 500 does not require support of any data center equipment racking but may contact the equipment racking if prescribed by design or user. In some embodiments, a coil 500 can be supported on a track and/or rollers in contact with the floor or flooring system. In some embodiments, a coil 500 can be suspended from overhead to the building structure. In some embodiments, a coil 500 can be supported by custom mounting frames or brackets supported overhead or from grade (see, e.g., FIG. 5E). This may be useful in areas that do not have much floor space.

For access to the equipment racks, a coil 500 can move or slide parallel to the equipment racks, swing similar to a door when mounted to hinges, or rise into the overhead ceiling or overhead space. In some embodiments, a coil 500 can be configured in a zig zag or overlapping for greater surface area exposed to the entering air.

To accommodate moving coils 500, the coil fluid line may be flexible or rigid, or may include a combination flex pipe with rigid pipe flex joints. In some embodiments, the cooling coil assembly may have fans and sensors connected to the coil 500 that will also have flexible connections and conductors that allow the coil 500 to be moved within a prescribed range to meet design requirements or user needs. In some embodiments, one or more of the fluid lines, electrical path, and sensor(s) can be designed to allow movement of a coil 500 to gain access to data center equipment.

In some embodiments, the coils 500 can be designed as passive coils, with no active external fan systems, and with all the air flows generated by the computing devices. In some embodiments, the coils 500 can be designed as active systems with fans 202 external to the computing devices at any location attached directly to the coil 500 or in proximity to the coil 500 and communicating through ducts or other enclosure or diverting system designed to channel air. The external fan system airflows can be constant of controlled variable speed and pressure.

Although FIGS. 1 through 5E illustrates example of a cooling system 100 and related details, various changes may be made to FIGS. 1 through 5E. For example, various components in the cooling system 100 may be combined, further subdivided, replicated, rearranged, or omitted and additional components may be added according to particular needs. As a particular example, in data centers with larger data halls 110, the cooling system 100 can include multiple fluid coolers 130, multiple MHACUs 114, and multiple pump packages 120 connected in parallel for common fluid connection of all components in the data hall 110. As another example, in some data halls, one or more computer room air handler (CRAH) units could be implemented in addition to, or lieu of, one or more of the MHACUs 114. In addition, while FIGS. 1 through 5E illustrate an example cooling system for use with data centers, the described functionality may be used in any other suitable device or system.

FIG. 6 illustrates an example of a computing device 600 for use in a cooling system according to this disclosure. The computing device 600 may be the computing device 140 discussed above in FIG. 1 . The computing device 600 can be configured to control operations in various components in the system 100. For example, the computing device 600 may control or monitor operations associated with the MHACU 114, the pump package 120, or the fluid cooler 130.

As shown in FIG. 6 , the computing device 600 includes a bus system 605, which supports communication between processor(s) 610, storage devices 615, communication interface (or circuit) 620, and input/output (I/O) unit 625. The processor(s) 610 executes instructions that may be loaded into a memory 630. The processor(s) 610 may include any suitable number(s) and type(s) of processors or other devices in any suitable arrangement. Example types of processor(s) 610 include microprocessors, microcontrollers, digital signal processors, field programmable gate arrays, application specific integrated circuits, and discrete circuitry.

The memory 630 and a persistent storage 635 are examples of storage devices 615, which represent any structure(s) capable of storing and facilitating retrieval of information (such as data, program code, and/or other suitable information on a temporary or permanent basis). The memory 630 may represent a random access memory or any other suitable volatile or non-volatile storage device(s). The persistent storage 635 may contain one or more components or devices supporting longer-term storage of data, such as a read-only memory, hard drive, Flash memory, or optical disc. For example, persistent storage 635 may store one or more databases of data, standards data, results, data, client applications, etc.

The communication interface 620 supports communications with other systems or devices. For example, the communication interface 620 could include a network interface card or a wireless transceiver facilitating communications over the system 100. The communication interface 620 may support communications through any suitable physical or wireless communication link(s). The I/O unit 625 allows for input and output of data. For example, the I/O unit 625 may provide a connection for user input through a keyboard, mouse, keypad, touchscreen, or other suitable input devices. The I/O unit 625 may also send output to a display, printer, or other suitable output devices.

Although FIG. 6 illustrates one example of a computing device 600, various changes may be made to FIG. 6 . For example, various components in FIG. 6 could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, while depicted as one system, the computing device 600 may include multiple computing systems that may be remotely located. In another example, different computing systems may provide some or all of the processing, storage, and/or communication resources according to this disclosure.

FIG. 7 is a flowchart illustrating an example of a cooling process 700 using the cooling system 100 of FIG. 1 according to various embodiments of the present disclosure. The embodiment of the cooling process 700 shown in FIG. 7 is for illustration only. Other embodiments of the cooling process 700 could be used without departing from the scope of this disclosure.

Referring to FIG. 7 , in operation 701, cooled supply fluid from the pump package 120 is supplied to the MHACUs 114 a-114 c via a fluid supply line 302. In operation 703, some or all of the cooled supply fluid from the pump package 120 is input into the MHACU 114 a, which is the first MHACU in the series. The fluid moves through one or more coils 206 in the MHACU 114 a, absorbing thermal energy from the air of the data hall 110. In operation 705, the temperature sensor 311 a measures that the fluid temperature in the MHACU 114 a rises to a temperature that is less than a predetermined maximum. In operation 707, in response to the measured temperature, the control valve 321 a is controlled to provide at least some of the fluid to the second MHACU 114 b. The fluid moves through one or more coils 206 in the MHACU 114 b, absorbing thermal energy from the air of the data hall 110. In operation 709, the temperature sensor 311 b measures that the fluid temperature in the MHACU 114 b rises to a temperature that is at least the predetermined maximum. In operation 711, in response to the measured temperature, the control valve 321 b is controlled to provide the fluid to the fluid return line 304. In operation 713, the heated fluid is returned to the pump package 120 via the fluid return line 304.

The process 700 discussed above illustrates example operations that can be implemented in accordance with the principles of the present disclosure, and various changes could be made to the process 700. For example, while shown as a series of steps, various steps in the process 700 could overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced by other steps.

Due to their importance, data centers are designed to operate with very high reliability and uptime. The requirements for reliability and uptime are primary elements of data center design and engineered systems.

As discussed above, data center engineered cooling solutions range from simple to complicated topologies that are comprised of basic mechanical and electrical components that require routine maintenance and may have catastrophic failures without warning. Thus, in data center cooling design, it is common to provide a solution that provides some level of redundancy. This redundancy is needed to provide the full cooling requirements of the rack, row, module, space, room, container or building during scheduled maintenance windows or unplanned outages.

To achieve the reliability of the designed systems, data center designers and engineers may provide redundant critical individual components to meet systems reliability and uptime requirements. In some embodiments, data center designers and engineers may provide alternative means and methods to provide reliability and uptime requirements.

In the simplest designs, with the lowest reliability, mechanical systems have one each of critical components. The capacity of the critical components is equal to the demand of the workload. In the most common redundancy scenario, Normal Plus One (“N+1”), the system includes one additional piece of critical equipment or increment of capacity. Most cloud data center designs include redundancy techniques and components as part of the design. The redundancy improves the reliability of the facility in terms of uptime for the computer equipment. In many systems, the uptime expectation is 99.999% uptime for the critical compute load. This is often described as “Five Nines uptime.”

The most efficient design in a data center uses air segregation (also known as containment) and MHACUs to achieve the best results. This air segregation requires the supply air stream and the return air stream to be isolated from each other through use of a physical barrier that prevents infiltration or mixing. This segregation forces the air through the engineered cooling path provided by the MHACU. In general, to achieve the most cost-effective and energy efficient design and insulation, longer and fewer containment paths should be used, so that fewer redundant components are required.

Within the data center industry, hyperscalers and colocation service providers have customer physical space requirements that range from a few data center racks of computing equipment to several hundred racks of computing equipment. Common requirements are twenty to one hundred racks. The racks are often arranged in the hot and cold aisle configuration discussed above. Data centers that are built for hyperscalers and other internet services clients generally have a security requirement to physically isolate the racks of one client from those of another. In most designs, this is as simple as a large room with cage type walls segregating the clients.

Air segregation modules typically include solid end cap walls that contain the hot aisle and prevent a person from touching or accessing the sequestered equipment of another. This security requirement causes data center designers to use small computing equipment rack rows (e.g., containing less than ten racks) and containment modules including small deployments, with the MHACUs providing cooling solutions. Each small containment module as a stand-alone space has the same redundancy requirements for cooling as a much larger module with several hundred racks. For example, each small containment module uses one additional MHACU unit than is required in order to meet the minimum cooling redundancy design of “N+1.” In a data center with many short containment modules, this represents an unnecessarily large quantity of redundant MHACU units.

To address these and other issues, various embodiments of this disclosure can include one or more vestibules that link two or more small containment modules for cooling redundancy purposes, while maintaining security for each short containment module.

FIGS. 8A through 8C illustrate different views of an example data hall 110 that includes one or more vestibules according to this disclosure. In particular, FIG. 8A illustrates a perspective view of the data hall 110, FIG. 8B illustrates an overhead plan view of the data hall 110, and FIG. 8C illustrates a perspective view of the data hall 110 with certain components removed to promote clarity and understanding. The embodiment of the data hall 110 shown in FIGS. 8A through 8C is for illustration only. Other embodiments of the data hall 110 could be used without departing from the scope of this disclosure.

As shown in FIGS. 8A through 8C, the data hall 110 includes multiple racks 801 of data equipment (e.g., servers 112) that are grouped into small containment modules 802 a-802 d. In some embodiments, each containment module 802 a-802 d represents the data equipment for one data center customer. The containment modules 802 a-802 d are “small” in that each containment module 802 a-802 d includes a few racks 801 (e.g., less than ten or twenty racks 801), as compared to a “large” containment module that can include dozens or hundreds of racks. Each containment module 802 a-802 d includes a hot aisle 803, and the racks 801 of each containment module 802 are arranged on opposite sides of the hot aisle 803. One or more MHACUs 114 are disposed above the hot aisle 803 of each containment module 802 a-802 d to provide cooling for the computing equipment in each containment module 802 a-802 d, as discussed above.

In conventional data halls, each containment module is generally segregated with regard to air movement. That is, the hot aisle of each containment module is segregated from hot aisles of other containment modules by solid walls or solid doors that restrict air movement between containment modules. In contrast, the data hall 110 includes multiple vestibules 804 a-804 b that permit the movement of air between two or more containment modules 802 a-802 d. That is, each vestibule 804 a-804 b provides a connected return air common plenum path for the hot air flow between two or more containment modules 802 a-802 d. For example, in FIG. 8B, the vestibule 804 a connects the hot aisles 803 of the containment modules 802 a and 802 b for air flow, and the vestibule 804 b connects the hot aisles 803 of the containment modules 802 c and 802 d for air flow. Each vestibule 804 a-804 b can be formed in any size or shape to provide a common non-directional air path that communicates with two or more individual hot aisles 803. As described in greater detail below, each vestibule 804 a-804 b also provides required or desired physical security using cage type or open-air flow type doors at certain locations to secure the data equipment but allow the hot air stream in each hot aisle 803 to move in any direction throughout the vestibule connected system.

The connected air path between multiple containment modules 802 a-802 d, as provided by the vestibules 804 a-804 b, allows for a reduction in the number of redundant MHACUs 114 in the data hall 110 while still meeting the requirements of “N+1” redundancy. For example, since the vestibule 804 a connects the hot aisles 803 of the containment modules 802 a and 802 b for air flow, it is not necessary for each of the containment modules 802 a and 802 b to have its own redundant MHACU 114. Instead, one redundant MHACU 114 can provide adequate redundancy for both containment modules 802 a and 802 b. Similarly, rather than each of the containment modules 802 c and 802 d having its own redundant MHACU 114, instead, one redundant MHACU 114 can provide adequate redundancy for both containment modules 802 c and 802 d.

Each vestibule 804 a-804 b can include both solid walls that are substantially or completely impervious to air flow, and mesh walls that easily permit the flow of air through the wall. The mesh walls of each vestibule 804 a-804 b form a physical barrier between the vestibule 804 a-804 b and the adjacent containment modules 802 a-802 d, while permitting bidirectional air flow through the mesh walls. For example, hot air can move from the hot aisle 803 of the containment module 802 a through a mesh wall between the hot aisle 803 and the vestibule 804 a, through the vestibule 804 a, through a second mesh wall between the hot aisle 803 of the containment module 802 b, and into the hot aisle 803 of the containment module 802 b. Hot air can also move in the opposite direction, from the containment module 802 b, through the vestibule 804 a (and through its mesh walls), and into the containment module 802 a. Each mesh wall can be formed of any suitable material(s) that facilitate air movement through the mesh wall while restricting movement of personnel, including steel mesh, screening material, and the like.

The other walls of each vestibule 804 a-804 b—which can include the ceiling, the floor, and the walls that are parallel to the rows of racks 801—can be formed as solid walls. The solid walls may be constructed from various air-impervious materials, including rigid materials, soft fabric type materials, rolled sheet materials, individual strips of material, and the like. Such materials may be clear, translucent, opaque, or a combination of these. The ceiling of each vestibule 804 a-804 b may be formed of the same material(s) as the ceiling material of the data hall 110, including but not limited to, plaster, drywall, drop ceiling panels and frames, a structural frame, a building or space floor or roof element, a steel container or module, or the like.

The materials forming the solid and mesh walls of each vestibule 804 a-804 b may be supported by, mounted to, or hung from any floor structure (on grade or raised), any overhead structure (including ceiling grid structures, beams and girders, floor or roof structures above), data center sub-structures designed as part of a containment system, data center equipment racking, one or more cables (e.g., steel, wire, rope, or the like), a framing system (formed from metal, plastic, composite, or the like), one or more vertical or horizonal grids or grills, and the like.

The interior of each vestibule 804 a-804 b may be accessed from one or more portals or passageways. For example, each vestibule 804 a-804 b may be accessed through one or more solid doors 805 on the supply air aisle(s). Each solid door 805 is impervious to air flow in order to isolate the hot aisle(s) 803 from the supply air aisle(s). Each solid door 805 may be clear, translucent, or opaque, and may be sealed as needed. Each vestibule 804 a-804 b may also be accessed from a hot aisle 803 through a solid or mesh cage type door 805 disposed in a mesh or solid wall. Any of the doors 805 may be alarmed doors for emergency egress. Any of the doors 805 may have locking devices to prevent unauthorized access. Any of the doors 805 may have panic hardware where required by building or fire code or preference.

While not specifically part of a vestibule 804 a-804 b, one or more security doors 806 may be disposed within the hot aisle 803 of one or more containment modules 802 a-802 d in order to isolate specific customer equipment within the containment module 802 a-802 d.

As shown in FIGS. 8A through 8C, the vestibules 804 a-804 b are arranged to fluidly connect containment modules 802 a-802 d that are linearly aligned with each other. However, vestibules can be configured in other arrangements so as to connect containment modules that are not in a linear arrangement.

FIGS. 9A through 9C illustrate different views of another example data hall 110 that includes one or more vestibules in a different configuration according to this disclosure. In particular, FIG. 9A illustrates a perspective view of the data hall 110, FIG. 9B illustrates an overhead plan view of the data hall 110, and FIG. 9C illustrates a heat map of the data hall 110. The embodiment of the data hall 110 shown in FIGS. 9A through 9C is for illustration only. Other embodiments of the data hall 110 could be used without departing from the scope of this disclosure.

As shown in FIGS. 9A through 9C, the data hall 110 includes multiple small containment modules 902 a-902 d, each including a hot aisle flanked with multiple racks of data equipment. The data hall 110 also includes a vestibule 904 that connects the hot aisles of all four containment modules 902 a-902 d. Similar to the vestibules 804 a-804 b, the vestibule 904 can include mesh walls and/or doors that align with the hot aisle of each containment module 902 a-902 d. Other walls and/or doors of the vestibule 904 can be solid to prevent air movement between the supply air aisles of the data hall 110 and the vestibule 904. As shown by the small arrows in FIG. 9B, hot air from one of the containment modules 902 a-902 d can flow through the vestibule 904 to any other of the containment modules 902 a-902 d. This is also shown in the heat map of FIG. 9C, where the H-shaped area 906 represents a single contiguous “hot aisle” that branches through all four containment modules 902 a-902 d. Thus, the vestibule 904 connects containment modules 902 a-902 d that are arranged linearly and also in parallel.

FIG. 10 illustrates another example data hall 110 that includes multiple vestibules in a grid configuration according to this disclosure. The embodiment of the data hall 110 shown in FIG. 10 is for illustration only. Other embodiments of the data hall 110 could be used without departing from the scope of this disclosure.

As shown in FIG. 10 , the data hall 110 includes multiple small containment modules 1002, each including a hot aisle flanked with multiple racks of data equipment. The data hall 110 also includes multiple vestibules 1004 disposed at points between adjacent containment modules 1002. Together, the vestibules 1004 connect the hot aisles of all of the containment modules 1002 in a single contiguous “hot aisle” grid. The data hall 110 also includes multiple expansion vestibules 1005 disposed at ends of the rows of the containment modules 1002, as shown in FIG. 10 . In order to expand the data hall 110, additional containment modules 1002 could be installed on the “open” end of one or more of the expansion vestibules 1005. The additional containment modules 1002 would then be connected to the “hot aisle” grid for cooling redundancy. The data hall 110 also includes termination points 1006 disposed at the other ends of the rows of the containment modules 1002. The termination points 1006 can include a solid door to allow personnel access to a containment module 1002.

While FIG. 10 shows the data hall 110 configured with vestibules 1004 forming a “hot aisle” grid, other embodiments could include vestibules that connect containment modules to form a circular or ring arrangement, a hub and spoke arrangement, or any other suitable configuration.

It may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “transmit,” “receive,” and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and/or. The phrase “associated with,” as well as derivatives thereof, means to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The phrase “such as,” when used among terms, means that the latter recited term(s) is(are) example(s) and not limitation(s) of the earlier recited term. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

Moreover, various functions described herein can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer-readable medium. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase “computer-readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer-readable medium” includes any type of medium capable of being accessed by a computer, such as read-only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer-readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory, computer-readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

Definitions for other certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases. Although the present disclosure has been described with an exemplary embodiment, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claim scope. The scope of the patented subject matter is defined by the claims. 

What is claimed is:
 1. A system comprising: multiple modular hot aisle cooling units (MHACUs) arranged in a series in a data hall, each MHACU configured to cool multiple servers in the data hall, the servers arranged in multiple containment modules within the data hall, each containment module comprising a hot aisle; multiple vestibules, each connected to the hot aisles of at least two of the multiple containment modules and configured to allow heated air to flow between the hot aisles; a pump package configured to provide cooling fluid to the multiple MHACUs; and at least one computing device configured to control at least one of air throughput, leaving air temperature, or leaving fluid temperature in each of the multiple MHACUs to customize cooling levels to different ones of the multiple containment modules.
 2. The system of claim 1, wherein each of the multiple vestibules comprises multiple mesh walls, each mesh wall disposed between that vestibule and one or more of the at least two containment modules, each mesh wall configured to allow the heated air to flow through that mesh wall while restricting movement of personnel through that mesh wall.
 3. The system of claim 2, wherein each of the multiple vestibules further comprises at least one solid wall and at least one door.
 4. The system of claim 1, further comprising: a first temperature sensor configured to measure a temperature of the cooling fluid in a first MHACU of the multiple MHACUs; and a second temperature sensor configured to measure a temperature of the cooling fluid in a second MHACU of the multiple MHACUs.
 5. The system of claim 4, further comprising: at least one coil disposed in the first MHACU, the at least one coil configured to transfer thermal energy from the heated air to the cooling fluid while the cooling fluid is conveyed through the at least one coil and the heated air passes over the at least one coil.
 6. The system of claim 5, wherein the heated air is heated by the multiple servers and flows from the multiple servers to the first MHACU.
 7. The system of claim 1, wherein each of the multiple MHACUs is disposed above, behind, or in front of the multiple servers.
 8. The system of claim 1, further comprising: one or more equipment sensors disposed adjacent to or within at least one of the multiple servers and communicatively coupled to the at least one computing device, the one or more equipment sensors configured to measure one or more properties of the multiple servers, the one or more equipment sensors comprising at least one of: a power sensor, a thermal sensor, a fan speed sensor, or a CPU sensor.
 9. The system of claim 1, wherein the at least one computing device is further configured to: determine that a temperature of the cooling fluid in a first MHACU among the multiple MHACUs has risen to a first temperature that is less than a predetermined maximum temperature; in response to the determination that the temperature of the cooling fluid in the first MHACU has risen to the first temperature, control the system to provide at least some of the cooling fluid to a second MHACU among the multiple MHACUs; determine that the temperature of the cooling fluid in the second MHACU has risen to a second temperature that is at least the predetermined maximum temperature; and in response to the determination that the temperature of the cooling fluid in the second MHACU has risen to the second temperature, control the system to provide the cooling fluid to a fluid return line for return to the pump package.
 10. The system of claim 9, wherein the at least one computing device is further configured to: calculate heat loads based on power demands of the multiple servers; and use the calculated heat loads to determine the customized cooling levels in different parts of the data hall.
 11. The system of claim 9, wherein the return fluid line comprises at least one immersion tank fluidly coupled between the multiple MHACUs and the pump package.
 12. The system of claim 1, further comprising: a fluid cooler configured to receive heated fluid from the multiple MHACUs via the pump package, cool the heated fluid to form the cooling fluid, and output the cooling fluid to the pump package.
 13. A method comprising: providing, via a fluid supply line, cooling fluid from a pump package to a first modular hot aisle cooling unit (MHACU) among multiple MHACUs arranged in a series in a data hall, each MHACU configured to cool multiple servers in the data hall, the servers arranged in multiple containment modules within the data hall, each containment module comprising a hot aisle, wherein at least some of the hot aisles are connected via multiple vestibules that allow heated air to flow between the at least some hot aisles; determining that a temperature of the cooling fluid in the first MHACU has risen to a first temperature that is less than a predetermined maximum temperature; in response to the determining that the temperature of the cooling fluid in the first MHACU has risen to the first temperature, providing at least some of the cooling fluid to a second MHACU among the multiple MHACUs; determining that the temperature of the cooling fluid in the second MHACU has risen to a second temperature that is at least the predetermined maximum temperature; and in response to the determining that the temperature of the cooling fluid in the second MHACU has risen to the second temperature, providing the cooling fluid to a fluid return line for return to the pump package.
 14. The method of claim 13, wherein each of the multiple vestibules comprises multiple mesh walls, each mesh wall disposed between that vestibule and one or more of the at least some hot aisles, each mesh wall configured to allow the heated air to flow through that mesh wall while restricting movement of personnel through that mesh wall.
 15. The method of claim 14, wherein each of the multiple vestibules further comprises at least one solid wall and at least one door.
 16. The method of claim 13, further comprising: measuring the temperature of the cooling fluid in the first MHACU using a first temperature sensor; and measuring the temperature of the cooling fluid in the second MHACU using a second temperature sensor.
 17. The method of claim 13, further comprising: transferring thermal energy from heated air to the cooling fluid, using at least one coil disposed in the first MHACU, while the cooling fluid is conveyed through the at least one coil and the heated air passes over the at least one coil.
 18. The method of claim 17, wherein the heated air is heated by the multiple servers and flows from the multiple servers to the first MHACU.
 19. The method of claim 18, wherein each of the multiple MHACUs is disposed above, behind, or in front of the multiple servers.
 20. The method of claim 13, further comprising: measuring one or more properties of the multiple servers using one or more equipment sensors disposed adjacent to or within at least one of the multiple servers, the one or more equipment sensors communicatively coupled to the at least one computing device, the one or more equipment sensors comprising at least one of: a power sensor, a thermal sensor, a fan speed sensor, or a CPU sensor. 